 $ type sys$update:VAXGKS030.RELEASE_NOTES


                     VAX GKS Version 3.0 Release Notes

     This document describes changes and corrections to  the  VAX  GKS
     V3.0  software and documentation.  Read it before you install VAX
     GKS.




     1  INSTALLATION NOTES

     1.1  Technical Notes

     1.1.1  Installing GKS On VAXclusters -

     If you are performing the GKS installation  in  a  cluster  which
     uses  a common system disk, set default to SYS$COMMON:[SYSUPD] to
     assure that GKS is installed on the common disk structure and not
     on  the  specific  disk  structure  of  the  node  on  which  the
     installation is being performed.




     2  ENHANCEMENTS IN THIS RELEASE

     The following list documents the features  that  distinguish  VAX
     GKS  V3.0  from  VAX  GKS  V2.0  and  refers to the corresponding
     sections in the VAX GKS Reference Manual:

      o  Event and  Sample  Input  Mode  -  For  complete  information
         concerning  these  input  modes,  refer  to  Chapter 6, Input
         Functions and to  Chapter  11,  Inquiry  Functions  (for  the
         inquire  functions  for  getting  information about the event
         queue).  For more information concerning the FORTRAN  binding
         equivalent  functions,  refer  to Chapter 10, FORTRAN Binding
         Functions.

      o  Generalized Drawing Primitives (GDPs) and Escapes -  VAX  GKS
         now  defines  many generalized drawing primitives and escapes
         available to many of the  supported  devices.   For  complete
         information, refer to Appendix I, GDPs and Escapes.

      o  Logical Input Device Numbers - In order to implement a  level
         2c  product,  VAX GKS increased the number of different input
         device numbers of each class.  VAX GKS now supports at  least
         four   device   numbers  for  each  input  class.   For  more
         information concerning the new logical input device  numbers,
         refer to Appendix J, VAX GKS Specific Input Values.

      o  Newly Supported Physical Devices - VAX GKS now  supports  the
         VAXstation II/RC, VAXstation 2000, VT330, VT340, LPS40, LA75,
         TEKTRONIX* 4107, and HP7475*.  For more information, refer to
         the appropriate device-specific appendix.











                                                                Page 2


      o  In addition, GKS supports  the  Digital  ScriptPrinter  as  a
         PostScript*  device.   This  device  is  not  documented as a
         supported PostScript* device but is supported by VAX GKS V3.0
         as a device of type GKS$K_POSTSCRIPT (value 61).  For further
         information about the PostScript* devices please see Appendix
         M, LPS40/PostScript* Workstation Specifics.

      o  There have been additional implementation dependent line  and
         marker  styles  added.   In  addition the predefined line and
         marker bundle  tables  for  devices  have  been  expanded  to
         contain  some  of  these forms and to make these bundles more
         consistent from device to device.  For  more  information  on
         which  devices  support  the  new  styles  and  what  the new
         predefined bundles are please refer to the appropriate device
         specific appendix.

      o  ReGIS output only (device type 10) now supports output  to  a
         file for the VT125 with color, VT240, VT240 with color, VT330
         and VT340.  Refer to  Appendix  L,  ReGIS  Graphics  Protocol
         Workstation Specifics for the proper bit mask and hexadecimal
         workstation identifier.

      o  CGM Output Metafile Format - VAX GKS  now  supports  the  CGM
         metafile  format  for clear-text and character-encoded output
         metafiles  only.   For  information  concerning  this   newly
         supported  metafile  format,  refer  to  Appendix  E, VAX GKS
         Metafile Structures (GKSM, CGM).

      o  Additional Bitmasks - The VT125, VT240, VT330,  VT340,  LCG01
         (formerly  LCP01),  LA50,  LA75,  and the CGM metafile output
         workstation now support the use of  Bitmasks  as  hexadecimal
         workstation  identifiers.  For more information, refer to the
         appropriate device-specific appendix.

      o  New Constants - To complement the  support  of  new  devices,
         escapes,  GDPs,  input  modes,  and so forth, VAX GKS now has
         additional defined constants.  For more  information,  review
         Appendix B, VAX GKS Constants.





     3  CHANGES IN THIS RELEASE

     The following list documents the changes  which  have  been  made
     which are incompatible with VAX GKS V2.0.

      o  Opening Multiple Workstations - If multiple workstations  are
         opened  each  must  have  a  unique connection identifier and
         workstation  type  pair.   This  most  strongly  affects  the
         VAXstation  handlers which used to allow multiple connections
         with GKS$K_CONID_DEFAULT and GKS$K_WSTYPE_DEFAULT.  Now  only
         the  first  connection  of this sort will be valid, all other
         connections must  have  a  different  connection  identifier.









                                                                Page 3


         This  change  was made to be more closely in conformance with
         the ISO and ANSI standards.

      o  VAXstation Hardware Fonts - The  numbers  of  the  VAXstation
         hardware  fonts  have  changed to avoid conflict with the VAX
         GKS software font numbers.  Old font number  1  is  now  also
         available  as  the font numbered -200.  Old font number -1 is
         now only available as font -201.  Old font number -2  is  now
         only  available as font -202.  Old font number -3 is now only
         available as font -203.  This has been done because the fonts
         are  now  available in stroke precision which would interfere
         with the current stroke fonts provided by VAX GKS.

      o  The VAXstation  marker  sizes  have  been  changed  to  allow
         minimal  regeneration  of  segments  containing markers.  The
         marker scale sizes available are 1.0, 2.2, 3.4, 4.6, and  6.2
         times  the  nominal size.  Requested marker scale factors are
         rounded  down  to  the  next  available  smaller  size.   For
         example,  a  marker  scale  factor  of  4.7 is displayed as a
         marker scale factor of 4.6.  Similarly, a marker scale factor
         of  2.0  is  rounded down to 1.0.  Scale factors smaller than
         the minimum (1.0) are displayed with a marker scale factor of
         1.0.

      o  VAXstation I Device Type Number -  The  VAXstation  I  device
         type  number  has  changed from the value 41 to the value 42.
         This has been done to more correctly  reflect  the  different
         aspect  ratio  of  a  VAXstation  I.  Although device 41 will
         still work on a VAXstation  I  it  will  produce  incorrectly
         sized windows and output.

      o  VAXstation Stroke Data Records - The VAXstation stroke  input
         devices no longer use the third component of the stroke input
         data record.  VAX GKS Version 2.0 used this  component  as  a
         time change interval.

      o  The default orientation for the LA50 printer has been changed
         to  LANDSCAPE  in  order  to be compatible with the other GKS
         supported sixel devices.  In order to get portrait  mode  you
         must  use  the appropriate hexadecimal workstation identifier
         and bit mask.  Please refer to the device appendix for  these
         values.

      o  Changes in the Version 2.0 Escape Numbers - VAX  GKS  Version
         2.0  supported three escape functions numbered -1, -2 and -4.
         Old escape number -1 (print screen)  is  now  numbered  -101.
         Old  escape  number  -2 (set pen speed) is now numbered -100.
         The old VAXstation escape -4 which was documented in the  VAX
         GKS  V2.0 release notes has been removed from this release of
         VAX GKS.  This is due to changes in  the  VAXstation  handler
         for  Version  3.0  of  VAX  GKS.  To see if a device supports
         these escapes, refer to Appendix I, VAX GKS GDPs and Escapes.









                                                                Page 4


      o  VAX GKS  V2.0  device  handlers  will  not  work  with  V3.0.
         Changes have been made to the device function table (DFT) and
         the workstation description table (WDT).  The WDT changes are
         mandatory while the DFT need only be reassembled and relinked
         to work properly.  Please review PART II of writing  VAX  GKS
         Graphics  Handlers  thoroughly  if  you  have  written a V2.0
         device handler.  VAX GKS V2.0 Workstation handlers must  also
         have  their device function tables recompiled and relinked to
         work with V3.0.




     4  RESTRICTIONS REMOVED

     4.1  Insert Segments And Metafiles


     GKS$INSERT_SEGMENT no longer causes an error  when  used  with  a
     metafile  output  workstation  and when the insert transformation
     matrix is not the identity matrix.



     4.2  Inquire Text Extent On VAXstations


     GKS$INQUIRE_TEXT_EXTENT no longer  returns  an  incorrect  extent
     rectangle when you call it on a VMS VAXstation.



     5  KNOWN PROBLEMS


     This section describes known technical problems in this release.



     5.1  VAXstation Pattern Output


     On VAXstations, patterns and fill areas  may  appear  misaligned.
     This  should only occur when the pattern is in a segment and part
     of that segment is  redrawn  with  the  boundary  of  the  redraw
     intersecting  a  portion of the patterened region.  The result of
     this will be  a  region  inside  the  patterned  fill  where  the
     patterns  don't match.  If the image must be absolutely correct a
     GKS$REDRAW_SEG_ON_WS will force the image to be correct.



     5.2  VAXstation Complement-mode Text Output









                                                                Page 5


     On VAXstations, certain sizes of text  contain  pixels  that  are
     drawn  twice.   This  is  caused by the software that manages the
     VAXstation display.  The result is that portions of the text seem
     to be reset to the background color.



     5.3  Resizing VAXstation Windows


     Resizing a VAXstation  window  while  an  input  operation  using
     Locator  PET  6  (digital locator) is active may make the locator
     disappear.



     5.4  VAXstation Scaled Text


     Scaled text drawn on a VAXstation may  not  appear  correct.   In
     particular text which has been scaled to a larger size may extend
     below its base line.  This is due  to  a  known  problem  in  the
     software that manages the VAXstation display.



     5.5  Setting ECHO/NOECHO With PICK On The VAXstation


     Turning echoing off and back on again with the  GKS$SET_PICK_MODE
     function  on  a VAXstation will cause the default pick cursor for
     the VAXstation ( a square sight) to be incorrectly replaced  with
     the  standard  VAXstation  arrow cursor.  The echoing will occur,
     but the  cursor  being  used  will  be  the  arrow.   A  call  to
     GKS$INIT_PICK will restore the cursor to the square sight.



     5.6  Fill Areas With 32,768 Points


     Fill areas with greater than 32,768 (32K) points  will  cause  an
     error  on  the  VAXstation.   The points may be drawn incorrectly
     when they exceed 32,768 in number.  This is a  known  restriction
     in the software that manages the workstation.



     5.7  Drawing Polymarkers Using The Erase Mode Escape


     When you draw a polymarker in erase mode  on  a  VAXstation,  the
     system  clears  the  entire  32 x 32 bit (cell) region instead of
     just the marker itself.  This  is  a  known  restriction  in  the
     software that manages the workstation.









                                                                Page 6


     5.8  ReGIS Cell Arrays


     A problem exists on all ReGIS devices except for the  VT340  with
     cell  arrays  when the resolution is less that 8 pixels per cell.
     One (or more) horizontal lines one pixel thick may  be  generated
     in  the  cell  array  in between rows of cells.  The lines can be
     eliminated by varying the size of the  cell  array  rectangle  by
     small amounts until the lines disappear.



     5.9  Incorrect Screen Regeneration With ReGIS Devices


     If GKS$SET_WS_VIEWPORT is called on a ReGIS device the screen  is
     not properly regenerated (the old image remains displayed) if the
     workstation  viewport  changed  and  the  regeneration  mode  was
     GKS$K_IRG_ALLOWED.   The  workaround  for  this  is  to  set  the
     regeneration   mode   to   GKS$K_IRG_SUPPRESSED,   perform    the
     GKS$SET_WS_VIEWPORT  function,  and  then call GKS$UPDATE_WS with
     the regeneration allowed parameter equal to GKS$K_IRG_ALLOWED.



     5.10  Pick Highlight Remaining  After  Delete  Segment  On  ReGIS
           Devices


     This problem occurs only on the VT125, VT240,  VT241,  VT330  and
     VT340.  It only occurs during sample or event pick mode with echo
     on  when  a  segment  which  overlaps  another   currently   pick
     highlighted  segment  by  a  single  pixel is deleted.  This will
     possibly leave a single row of highlight pixels.  There  are  two
     possible  workarounds  to  this problem if you find it occurring.
     The first is to set the pick input mode  to  request  before  the
     segment  is  deleted.   Because  the  pick  input would be off no
     segment would be pick  highlighted  and  the  problem  could  not
     occur.   The second less efficient solution is to set the devices
     regeneration  mode  to  GKS$K_IRG_SUPPRESSED  which  avoids   the
     optimized regeneration which has the problem.



     5.11  ReGIS Devices And Input Overflow


     If a user causes the VMS terminal  input  queue  to  overflow  (a
     condition  signaled  by  a beep) while entering GKS input GKS can
     become stuck in a hibernate state.  To avoid this the  user  must
     not  enter  so many keystrokes that the VMS buffer overflows.  To
     this  end  the  user  must  be  aware  if  the  current  echo  is
     significantly  behind  the  keystrokes  that  have  been entered.
     Accidental occurences caused by AUTO REPEAT  can  be  avoided  by
     disabling  the  AUTO REPEAT ability on terminals which allow that









                                                                Page 7


     ability to be disabled (for example the VT240, VT330 and VT340).



     5.12  Pick Highlight Remaining After GKS$CLEAR_WS


     If during event or  sample  mode  pick  a  clear  workstation  is
     performed  while a segment is pick highlighted the Pick highlight
     will be replaced on the display even though the segment is  gone.
     As soon as the operator moves the pick cursor again the highlight
     will be removed.  If you feel you must work around  this  problem
     it  can  be  avoided  by  setting  the pick input mode to request
     before the screen is cleared and restoring the input  mode  after
     the clear.



     5.13  PostScript* Device And GKS$SET_PAT_REP


     If a pattern which already has a representation is set to  either
     a  smaller  or  larger  pattern  the  PostScript* workstation may
     access violate or  return  error  -90  (VAXGKS$_ERROR_NEG_90  Bad
     Memory  address freed in routine ****).  To avoid this always use
     an uninitialized pattern index to set.  The  pattern  indexes  30
     through 255 are uninitialized on the postscript device and so can
     be used without this problem occurring.



     5.14  Incorrect Segment Regeneration Of Hollow Fill Areas


     Hollow fill areas may be incorrectly regenerated on  all  devices
     except  the  VAXstation  if the region which requires update does
     not fully include the hollow fill area.  The result  will  be  be
     additional  vertical  and/or horizontal lines in the filled area.
     The image can be forced to be correctly displayed by performing a
     redraw using GKS$REDRAW_SEG_ON_WS.



     5.15  Segment Simulation In Workstation Handlers


     When inserting a segment from WISS to a workstation that uses the
     provided   segment   simulation,   pick  identifiers  may  become
     incorrect.  This problem only  affects  workstation  handlers  of
     class  OUTIN  which  use the Segment Simulation we provide.  This
     problem does not affect any DIGITAL supported device, nor does it
     affect  any  device  handlers that may exist.  You can avoid this
     problem  by  supporting  the  device  with  the  device   handler
     interface, instead of the workstation handler interface.








                                                                Page 8


     5.16  Incorrect Exit On Running Out Of Virtual Memory


     If sufficient segments are created on WISS or  on  a  PostScript*
     device  to  cause  VAX  GKS  to run out of process virtual memory
     space VAX GKS does not always detect the condition and issue  the
     -92 error (VAXGKS$_ERROR_NEG_92 Internal GKS error:  Insufficient
     virtual memory in routine ****).  Because VAX GKS fails to detect
     the  condition  it  will  usually fail due to an access violation
     when it tries to access the invalid memory.



     5.17  Several Escapes Not Working

     The escape GKS$K_ESC_MAP_NDC_OF_WC  (-400)  does  not  work.   If
     called  it  may  access  violate or produce invalid results.  The
     escape GKS$K_ESC_MAP_DC_OF_NDC (-401) may also access violate  or
     produce  incorrect  results.   The escape GKS$K_ESC_MAP_WC_OF_NDC
     (-402) will return invalid or incorrect results.  Last of all the
     escape GKS$K_ESC_MAP_NDC_OF_DC will incorrectly return error 182,
     (GKS$_ERROR_182 Contents of escape data  record  are  invalid  in
     routine ***).



     5.18  Invalid Data To Certain Arc GDPS


     The GDPs GKS$K_GDP_ARC_2PT_RAD  and  GKS$K_GDP_FARC_2PT_RAD  will
     accept incorrect data.  Any positive radius will be accepted, but
     if the magnitude of the radius is not at least half the  distance
     between the two points a fatal error caused by an improper square
     root may occur.  To avoid this make sure  the  magnitude  of  the
     radius  vector  is at least half as large as the distance between
     the two points given to this GDP.



     5.19  Invalid Data And Choice Initialization


     The function GKS$INIT_CHOICE does not check  the  initial  status
     value.    If   a   value   of   other   than  GKS$K_STATUS_OK  or
     GKS$K_STATUS_NOCHOICE is passed to  GKS$INIT_CHOICE  choice  will
     act  incorrectly,  usually  by highlighting multiple choices at a
     time.  This can be avoided by making sure one of the two  allowed
     values is passed for the initial status value.



     6  KNOWN RESTRICTIONS


     This section describes the known restrictions in this release  of









                                                                Page 9


     VAX GKS.



     6.1  Writing To VT330 Or VT340


     To make the fullest use of the VT330 and VT340  devices  VAX  GKS
     keeps  them  in ReGIS graphics mode while the workstation remains
     open.  Because of this ASCII  text  sent  to  the  screen  via  a
     FORTRAN  WRITE  or  similar statements in other languages will be
     interpreted as ReGIS commands which can leave the terminal in  an
     unpredictable  state.   To  avoid  this  never  place text on the
     screen when the workstation is open unless you use  the  GKS$TEXT
     or GKS$MESSAGE functions.  It is recommended that when VAX GKS is
     used with the VT330 or VT340 that the  error  file  specified  in
     GKS$OPEN_GKS  be directed to a file to avoid having VAX GKS issue
     error messages to the terminal.  It is also recommended  the  you
     use  the  VMS  command  $  SET  TERMINAL  /NOBROADCAST to prevent
     messages sent to the terminal  by  VMS  from  causing  a  similar
     problem.



     6.2  Use Of Set Host And GKS


     Because the protocol used for set  host  favors  writing  to  the
     terminal  over  reading  from it it is possible to lock out event
     and sample input from GKS with an application which does a  great
     deal  of  screen updating.  This is most likely on the TEKTRONIX*
     4014, VT330 and VT340 because all  of  these  depend  on  complex
     read/write  protocols  to receive positional information from the
     device.  There are three methods  to  avoid  this  problem.   The
     first  is to avoid using set host with this class of application.
     The second is to avoid using sample and event mode input  if  the
     application  is going to be used with set host.  The final method
     is to have the application cease output at a regular interval  to
     allow the pending reads from the device to complete.



     6.3  Invalid Characters And VT330 Or VT340


     Passing 8  bit  control  characters  in  strings  which  will  be
     displayed (for example strings passed to GKS$TEXT or GKS$MESSAGE)
     may cause these devices to  exit  graphics  mode.   This  can  be
     avoided by not passing 8 bit controls in strings.



     6.4  Ada* Language Restrictions









                                                               Page 10


      o  Floating point OUTPUT parameters  to  GKS  inquiry  functions
         should  be  initialized  to  some  value  before  making  the
         function call.  This will avoid a possible  reserved  operand
         fault  if  GKS reports an error in the error parameter of the
         function.  In that  case  the  other  parameters  might  have
         uninitialized  values  (values returned from a failed inquiry
         call are left undefined according to the standard)  and  Ada*
         would copy these invalid values back to the original variable
         causing a reserved operand fault.

      o  Applications using Ada* tasks should make sure that GKS calls
         are  all  performed  from  the  same Ada* task or that proper
         synchronization is done.




     7  DOCUMENTATION NOTES

     7.1  VAX GKS Reference Manual - Volume I

     7.1.1  Documentation Additions -

     The new chapter sections and appendixes of the VAX GKS  Reference
     Manual include the following sections:

      o  The sections of Chapter 6, Input Functions, describing sample
         and   event   mode   input   (required   for   a   level   2c
         implementation).

      o  The  sections  of  Chapter  10,  FORTRAN  Binding  Functions,
         describing the sample and event binding functions.

      o  The sections of Chapter  11,  Inquiry  Functions,  describing
         GKS$INQ_INPUT_QUEUE_OVERFLOW and GKS$INQ_MORE_SIMUL_EVENTS.

      o  The sections of Appendix C,  Initial  Attributes,  describing
         the new VAX GKS specific line and marker types.

      o  The section of Chapter 8, Metafile Functions, describing  CGM
         formatted metafiles.

      o  Appendix I, GDPs and Escapes,  describing  the  new  VAX  GKS
         specific Generalized Drawing Primitives (GDPs) and escapes.

      o  Appendix J, VAX GKS Specific Input Values, describing the VAX
         GKS  logical  input  devices,  prompt  and  echo  types, data
         records, and input keypad functionality  (formerly  found  in
         each device-specific appendix).

      o  Appendix R, TEKTRONIX* 4107 Workstation Specifics, describing
         the newly supported TEKTRONIX* 4100 series of devices.











                                                               Page 11


     7.1.2  Documentation Errors -

     The following includes the  documentation  errors  and  omissions
     found in the VAX GKS Reference Manual:

      o  Pattern and Hatch Values -20 through -33 are invalid on ReGIS
         devices .  You can find the valid values in Appendix L, ReGIS
         Graphics Protocol Workstation Specifics.  This  is  described
         in that appendix, but may be misinterpreted.

      o  Use the DCL command  $SET  TERMINAL/NOWRAP  when  typing  out
         files  created  with  workstation type value 10 (ReGIS output
         only) to ensure that carriage returns are  not  written  into
         the   file.    See   Appendix   L,  ReGIS  Graphics  Protocol
         Workstation  Specifics,  for  more  information  about  ReGIS
         output.




     7.2  VAX GKS Reference Manual - Volume II

     7.2.1  Documentation Errors -

     The default status for pick and choice input have  been  changed.
     The  default  pick  status  is  now  GKS$K_STATUS_NOPICK  and the
     initial choice is now  GKS$K_STATUS_NOCHOICE.   Previously  these
     values  were  both GKS$K_STATUS_OK.  On many devices choice 1 was
     previously highlighted by  default.   Now,  no  choices  will  be
     highlighted until the operator takes some action, or if the input
     device is initialized to some other value.   These  changes  have
     been made to provide conformance with the ANSI and ISO standards.
     These changes affect all OUTIN devices.



     7.3  Writing VAX GKS Graphics Handlers

     7.3.1  Documentation Additions -

     Writing VAX GKS Graphics Handlers  now  contains  information  on
     building GKS level 2c handlers.

     Part II, which discusses building a Device  Handler  system,  has
     been   reformatted.   Descriptions  of  two  new  Device  Handler
     functions, Set Clipping and Free WDT, have been added to  Chapter
     4.  In addition, change bars in Chapter 3 indicate changes in the
     required data structures for Device Handler systems.

     Note that  because  Part  II  of  this  manual  now  contains  an
     additional  chapter,  the  chapter  numbers in Part III have each
     increased  by  one.   Chapter  8,   Workstation   Handler   Input
     Functions,  now  contains  descriptions  of  additional functions
     required for Sample mode input.








                                                               Page 12


     7.3.2  Documentation Errors -

     Make the following changes  in  Chapter  8,  Workstation  Handler
     Input Functions.

     Two output parameters for function  SAMPLE  PICK  are  incorrect.
     They should read as follows:

      o  STATUS Integer.  The pick status, either GKS$K_STATUS_OK  (1)
         or GKS$K_STATUS_NOPICK (2)

      o  PICK_ID Integer.  The pick ID of the picked primitive.   This
         is valid only if STATUS is GKS$K_STATUS_OK


     Status code GKS$_ERROR_142  is  incorrect.   It  should  read  as
     follows:

      o  GKS$_ERROR_142 Specified input device is not in sample mode.


     For function SAMPLE CHOICE, the value  for  GKS$K_STATUS_NOCHOICE
     is incorrectly written as 0.  It should be 2.




     7.3.3  Technical Notes -

     Note  that  the  device  handler   Clear   Workstation   function
     (described  in  Chapter  4) should only clear the output viewport
     and not any of the input viewports.  Therefore, any input  echoes
     that  are  defined  to  be in ECHO_AREA_SETs other then 0 must be
     UNAFFECTED by a clear workstation operation.

     Also note  that  for  the  workstation  handler  Escape  function
     (described  in  Chapter  7),  when  the  kernel calls your Escape
     routine with an escape function that requires a workstation type,
     it  sets  the WSL parameter to null (0).  This occurs because the
     device identified by the workstation type may not  be  open.   An
     example   is   GKS$K_ESCAPE_INQ_LIST_ESCAPE   for   a  particular
     workstation type.   In  this  case,  the  kernel  will  load  the
     workstation  identified  in  the  workstation  type  and call its
     escape function.




     * TEKTRONIX is a trademark of TEKTRONIX, Inc.

     * PostScript is a trademark of Adobe Systems, Inc.

     * Ada is a registered trademark  of  the  U.S.   Government  (Ada
     Joint Program Office)








                                                               Page 13


     HP7475 is a registered trademark of Hewlett Packard.

 $ 